In scripter lingo, ScriptSynch is a system extension that can provide functionality resembling “attachability” to your applications. To mortals, this means ScriptSynch can automatically launch applications, open files, or run scripts when specific applications launch or quit. This is useful for running a “startup script” whenever an application loads, attaching one application to another so they launch and quit at the same time (Eudora and Nuntius, for example), or tracking application usage through scripting. A little contrary to its name, ScriptSynch works fine without AppleScript, although it works best in conjunction with it.
ScriptSynch REQUIRES A MACINTOSH RUNNING SYSTEM 7 OR LATER. If you’re not running System 7, run, do not walk, to an Apple dealer and get up to date.
ScriptSynch is fully functional, but is shareware $10 US. Please encourage the shareware system and pay for software you use. Read on for details.
How do I install ScriptSynch?
Drag it to your System Folder. Your Mac is smart — it will put it where it belongs.
How do I use ScriptSynch?
Simple. When you first restart with ScriptSynch installed, you will notice a new folder called “ScriptSynch Aliases” in your Preferences folder. You can create it yourself if you’re the gung-ho type. Whenever an application starts up, ScriptSynch will look for an item in that folder called “<Application Name> launch” (ex: “SimpleText launch”). Likewise, whenever an application quits, ScriptSynch will look for an item called “<Application Name> quit” (ex: “SimpleText quit”). Different things happen depending on what this item is:
• If the item is an application (Or an alias to an application), ScriptSynch launches that application into the background (presumably, you don’t want it popping up in front of the program you’re trying to launch).
• If the item is a file (Or an alias to a file), ScriptSynch will ask the Finder to open that file.
• If the item is a script (Or an alias to a script), ScriptSynch will run that script. See the notes on scripts below for more on this.
• If the item is a folder (Or an alias to a folder), ScriptSynch will process each item in that folder as described above. This allows you to attach more than one item to an application. Folders can contain other folders.
ScriptSynch even detects invisible applications, so you can “attach” scripts or other applications to certain screen savers or extensions that are written this way. ScriptSynch itself is an invisible application, and you can attach items to it, too! (Items attached to ScriptSynch in this way would be opened at startup). Also remember that the Finder is an application like any other.
ScriptSynch will automatically quit any applications it launched when the application that caused the launches quits. In this way, you can “synchronize” applications so they launch and quit together. If you do not want applications to quit when their “parent” application quits, put a bullet (“•”) in the name of the alias in your ScriptSynch Aliases folder. Applications with bullets in the name of their alias will not be quit when their “parent” application quits.
Notes on scripts
A few words on how ScriptSynch handles scripts are in order. Depending on how your script is saved, it will be treated differently:
• If your script is saved as “text only” (uncompiled), it is treated as a document and opened.
• If your script is saved as an application, it is treated as such and launched. (i.e., you get your own entry on the Application Menu and everything). Note that unless you put a bullet in the name of the alias to your script, this means the script will be sent a “quit” event when the “parent” application quits. See above for more details.
• If your script is saved in compiled form, it is run. Keep in mind that ScriptSynch is invisible, so your script can’t open any windows or otherwise interact with the user; you’ll get an error if you try to pull this off. You can, of course, direct other applications to interact with the user or launch an applet of your design from your script to do this work.
• If AppleScript is not present on your System, ScriptSynch utterly ignores scripts or aliases to scripts in your ScriptSynch Aliases folder.
Who are you?
Just a guy. Other cool things I’ve written include:
• File Tracker, a utility that can “watch” files and/or folders on your hard drive and take action when things happen to them. This is great for tracking files over a network, automating tasks, creating “drop boxes”, keeping an eye on important documents, etc. File Tracker is shareware $15US.
• Script Hider, which does just what it says and makes scripts invisible so people like students using a lab can’t quit a monitoring “stay-open” script. Script Hider is free.
I’m hard at work on the next “killer app”, but there was a need for ScriptSynch, so here it is. Everything mentioned above, and ScriptSynch, are available from your favorite InterNet FTP site, commercial BBS systems, and probably local BBSs and user groups. If your favorite service doesn’t have a copy of what you’re looking for, let me know and I’ll send you a copy.
How can I pay for ScriptSynch?
Fill out the registration form included with ScriptSynch and send with a cheque, money order, or cash in the amount of $10, US dollars, (Canucks: equivalent Canadian is fine, too!) made out to Mark Aiken to:
Mark Aiken
4220 Kensington ave.
Montreal, Quebec,
H4B-2W1, CANADA
By registering your copy, you’ll be supporting the shareware system, which makes high-quality software available to people across the globe for ridiculously low prices. Don’t abuse this precious resource — register your copy if you use it.
Special pricing for site licenses (quantity purchasing) is available. Read the license agreement below for details on ScriptSynch’s licensing. Contact the author for bulk purchase discount information.
How can I reach you?
Write to Mark Aiken at:
InterNet: marka@ee.mcgill.ca
FidoNet: Sysop or Mark Aiken at node 1:167/106
FAX: (514) 486-8695
BBS: Mail to Sysop or Mark Aiken at (514) 486-3454 (This is the FidoNet node mentioned above)
Snail Mail: see registration info.
if you have questions or suggestions, I would love to hear from you; drop me a line. I can e-mail copies of software to people who can’t get their hands on it otherwise, and I’m more than happy to provide full support for my products.
Where’s the fine print?
Here. Have fun!
Terms of usage
In this document, “software” refers to all computer programs, codes, or documents included with this document, or any copy of any part of the items mentioned above. “you” refers to any entity that acquires this software.
You are licensed to use the software provided you respect the following terms:
You may:
1. Use the software for the purpose of evaluating it for a period of time not exceeding one month, beginning at the date that you begin using the software.
2. Redistribute the software to any person or organization, provided you redistribute a package identical to the one you obtained.
3. Use the software on as many computers as you like as long as you are the sole user of the software (ex: A single person installing the software on both his/her work and home machine, for personal use).
4. In lieu of 3), you may install the software on ONLY one (1) computer for use by several people (ex: A person installing the software on a server or lab computer functioning for the benefit of many).
4. Make as many backup copies as you like of the software.
You may NOT:
1. Install the software on multiple computers for use by multiple people simultaneously. Such usage is governed by a site license.
2. Alter the software in any way.
3. Redistribute the software in an altered form.
4. Redistribute the software as a package that differs in any way from the one you obtained. (i.e., you may not add or remove elements of the package when redistributing it, or distribute any altered versions of the original elements).
You must:
1. Register the software by sending in the registration form with any applicable fees (Registration instructions are given in the documentation) after your evaluation period. Registered software is restricted to the terms above — organizations wishing to use the software under circumstances not covered above must contact the author for further licensing information.
Redistribution
This software may be distributed via any means, physical or electronic. Excluded from this statement are organizations wishing to distribute this software in a commercial compilation, or organizations wishing to redistribute this software for profit. Such organizations must contact the author for written authorization to distribute the software. Permission is hereby granted for organizations wishing to distribute the software in non-commercial compilations (i.e., ones which are made available solely for the cost of materials, shipping, etc.), to do so.
Disclaimer of warranty
Mark Aiken hereby disclaims all warranties relating to this software, whether express or implied, including without limitation any implied warranties of merchantability or fitness for a particular purpose. Mark Aiken will not be liable for any special, incidental, consequential, indirect or similar damages due to loss of data or any other reason, even if Mark Aiken or an agent of his has been advised of the possibility of such damages. In no event shall Mark Aiken be liable for any damages, regardless of the form of the claim. The person using the software bears all risk as to the quality and performance of the software.
US Government:
Government End Users: If you are acquiring the Software on behalf of any unit or agency of the United States Government, the following provisions apply. The Government agrees:
(i) if the Software is supplied to the Department of Defense (DoD), the Software is classified as “Commercial Computer Software” and the Government is acquiring only “restricted rights” in the Software and its documentation as that term is defined in Clause 252.227-7013(c)(1) of the DFARS; and
(ii) if the Software is supplied to any unit or agency of the United States Government other than DoD, the Government’s rights in the Software and its documentation will be as defined in Clause 52.227-19(c)(2) of the FAR or, in the case of NASA, in Clause 18-52.227-86(d) of the NASA Supplement to the FAR.
Complete agreement
This agreement constitutes the entire agreement and supersedes any prior agreements between you and the author concerning this software. This agreement cannot be amended, modified, or waived except in writing.
General
If any provision of this agreement shall be found to be unenforceable, it shall be deemed severed from the remainder of this agreement.
